Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calendar Graph #1984

Open
1 task done
MrT3acher opened this issue Aug 10, 2022 · 8 comments · May be fixed by #4419
Open
1 task done

Calendar Graph #1984

MrT3acher opened this issue Aug 10, 2022 · 8 comments · May be fixed by #4419
Labels
area:status-page Everything related to the status page feature-request Request for new features to be added

Comments

@MrT3acher
Copy link

MrT3acher commented Aug 10, 2022

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

Current graph isn't optimized to show a lot of days (for example one year).
If it can show one year's data, It isn't so clear for user to understand it.

✔️ Solution

Use this Calendar Graph library in JS to show a large period of time Uptime:
https://www.npmjs.com/package/calendar-graph

For each day, you should specify a count number, which is the number of heartbeats / max_heartbeats_in_day * 100 (this is my proposal).

❓ Alternatives

No response

📝 Additional Context

No response

@MrT3acher MrT3acher added the feature-request Request for new features to be added label Aug 10, 2022
@shdf2
Copy link

shdf2 commented May 25, 2023

hello,
i'd like to see the Overall Uptime, like UptimeRobot is doing in their status page :
image

And the calendar view :
image

@Jamie-TinyPixel
Copy link

Has this gotten anywhere? I'd love to see this implemented!

@CommanderStorm
Copy link
Collaborator

Has this gotten anywhere?

Until now, nobody has provided a PR

@CommanderStorm
Copy link
Collaborator

@AlivaTH
Please refrain from posting +1 / requests for updates things on issues, as this makes issue-management harder.
Issues are for discussing what needs to be done how by whom.
We use 👍🏻 on issues to prioritise work, as always: Pull Requests welcome.

@CommanderStorm CommanderStorm added the area:status-page Everything related to the status page label Dec 8, 2023
@akhileshsooji028 akhileshsooji028 linked a pull request Jan 24, 2024 that will close this issue
7 tasks
@Zaid-maker
Copy link
Contributor

Zaid-maker commented Jan 26, 2024

That graph looks like Github Activity chart Lol. I don't think this make sense to change the whole Chart UI for which the Uptime Kuma is famous.

@wzrdtales
Copy link

uptime kuma is not famous for it. I think there is a misperception of reality here. Everyone single person that saw this graph of uptime kuma just scratched their head and the questions are always the same:

  • Why the hell is there only 40 minutes history on the graph
  • Where is the long term history (calendar)

@CommanderStorm
Copy link
Collaborator

@wzrdtales
I don't think your assumption is entirely true.
I assume Some people would like to not be as transparent with the public status of their system and would thus not like the last year of production outages to be displayed.
=> making the display option configurable is a better choice

@Zaid-maker
As long as this is configurable, such an alternate display mode is fine by me (#4419 (review))

@wzrdtales
Copy link

I assume Some people would like to not be as transparent with the public status of their system and would thus not like the last year of production outages to be displayed.

Those some people probably have a lot of downtimes and lie to their customers. Customers want transparency, and honest providers that actually do the invest for the uptime want to give them the transparency. That is the default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:status-page Everything related to the status page feature-request Request for new features to be added
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants